home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group92c.txt
/
000028_icon-group-sender _Fri Oct 2 02:45:23 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1993-01-04
|
2KB
Received: by cheltenham.cs.arizona.edu; Tue, 20 Oct 1992 09:17:32 MST
Date: 2 Oct 92 02:45:23 GMT
From: uchinews!ellis!goer@uunet.uu.net (Richard L. Goerwitz)
Organization: University of Chicago Computing Organizations
Subject: Re: Unix Logging Out
Message-Id: <1992Oct2.024523.2937@midway.uchicago.edu>
References: <01GPFIYT5FTU8WWF6P@mis.mcw.edu>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
TENAGLIA@mis.mcw.edu (Chris Tenaglia - 257-8765) writes:
>
>If I have a simple abc menu that looks something like :
>
> M : MAIL
> C : CHANGE PASSWORD
> L : LOGOUT
>
>Is there a way to log out cleanly?
Under UNIX, processes like shells (i.e. command interpreters) normally
get run right on login, and unless you "exec" a program (and overlay
that shell), it waits for your application to finish, then resumes its
work. Under normal circumstances, you can't log out from any of your
login shell's child processes. You have to quit everything else, and
jump back to the login shell and log out from there.
You could get around this a) by finding your login shell and then
killing it manually (a la system("kill -9 "||process_id) where pro-
cess_id is the ID of your login shell. This is very un-UNIXish. It's
normally presumed that one will not *want* to log out with processes
still active.
Does this make any sense?
--
-Richard L. Goerwitz goer%midway@uchicago.bitnet
goer@midway.uchicago.edu rutgers!oddjob!ellis!goer